← Back to issue list

patchelf warning / binary segfaults

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1753995
Type
issue
State
open
Author
~sajoupa
Labels
Created
2018-03-07 11:01:28.038516+00:00
Updated
2019-11-11 00:51:40.925784+00:00
Closed

Current evaluation

No evaluation has been recorded for this issue yet.

Issue body

Hi, I'm trying to snap telegraf (https://github.com/influxdata/telegraf), which is written in go. At the prime step, I get the following messages: [...] Priming telegraf patchelf: cannot find section '' Failed to update '/home/ubuntu/git/dev/telegraf/prime/bin/telegraf'. Retrying after stripping the .note.go.buildid from the elf file. Snapping 'telegraf' - Snapped telegraf_1.5.2_amd64.snap After installing and running the snap, it quickly enters Failed state (inactive (dead) (Result: core-dump)). syslog messages: https://pastebin.canonical.com/p/vzy6Pk9m5z/ dmesg: https://pastebin.canonical.com/p/PQJXM7n8Cv/ systemd service configuration (automatically generated): https://pastebin.canonical.com/p/qDp7ZbSwGN/ snapcraft file: https://pastebin.canonical.com/p/FQYWBWy25N/ This is using the stable snapcraft snap, 2.39.2 rev 1177 at the moment. The same problem does not happen with snapcraft 2.34+17.10 (deb from archives on an artful machine). This look very similar to lp:1736861, which is 'fix released'. I tried using snapcraft from --channel edge/patchelf-go. Got a warning: Files in this part are going to be patched to execute correctly on diverse environments. To disable this behavior set `build-attributes: [no-patchelf]` for the part. After adding `build-attributes: [no-patchelf]` the snap built and ran successfully, but I'm pretty sure the patchelf step is needed for the snap to run correctly on all the machines where it should be able to. Thanks.

Evaluation history

No evaluation history available.